Skip to main content
TrustRadius
SolarWinds Loggly

SolarWinds Loggly

Overview

What is SolarWinds Loggly?

Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.

Read more
Recent Reviews

TrustRadius Insights

Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. …
Continue reading

Loggly rocks

8 out of 10
December 15, 2020
Incentivized
Loggly is a neat a straight forward product. We use to centralize most of our application and security logs, including WAF data which we …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing

Standard

$79

Cloud
per month/billed annually

Pro

$159

Cloud
per month/billed annually

Enterprise

$279

Cloud
per month/billed annually

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.loggly.com/plans-and-pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is SolarWinds Loggly?

Unified Log Analysis and Log Monitoring

With environments spanning on-premises, hybrid, and public cloud environments, IT operations and application teams are inundated with unrelated events, issues, and logs. Every outage or slowdown directly impacts the business, either in lost productivity or lost revenue. Issues must be diagnosed rapidly and resolved across all the dynamically changing components underpinning your heterogeneous web applications, services, and infrastructure.

SolarWinds® Loggly® is presented by the vendor as a cost-effective, hosted, and scalable full-stack, multi-source log management solution combining powerful search and analytics with comprehensive alerting, dashboarding, and reporting to proactively identify problems and significantly reduce Mean Time to Repair (MTTR).

SolarWinds Loggly Features

  • Supported: Highly responsive search at scale
  • Supported: Interactive shareable dashboards
  • Supported: Anomaly detection and alerts
  • Supported: Dynamic Field Explorer™
  • Supported: Rapidly pinpoint bottlenecks and failure points
  • Supported: Collaborate with all stakeholders
  • Supported: New shared agent that collects metrics and logs
  • Supported: Add trace context to your logs

SolarWinds Loggly Screenshots

Screenshot of Streamlined Log AnalysisScreenshot of Monitoring & AlertingScreenshot of Screenshot of Screenshot of

SolarWinds Loggly Integrations

SolarWinds Loggly Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported CountriesAll
Supported LanguagesEnglish, Spanish

Frequently Asked Questions

Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.

Splunk Enterprise, Sumo Logic, and Rapid7 InsightOps are common alternatives for SolarWinds Loggly.

Reviewers rate Usability highest, with a score of 7.8.

The most common users of SolarWinds Loggly are from Small Businesses (1-50 employees).

SolarWinds Loggly Customer Size Distribution

Consumers0%
Small Businesses (1-50 employees)25%
Mid-Size Companies (51-500 employees)50%
Enterprises (more than 500 employees)25%
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(79)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. With its syslog digest capabilities, users can sift through logs to identify the root cause of outages and errors, creating alerts for future prevention. By serving as an aggregation point for streaming logs from network access switches and core routers, Loggly efficiently manages large volumes of data. This makes it a valuable tool for support and engineering teams, providing alerting, monitoring, and issue triage solutions. Additionally, Loggly acts as a central repository for logs from PHP-based apps and servers, offering reports, analysis, and aggregation from different sources. Its flexibility extends to monitoring and debugging large-scale application platforms leveraging multiple microservices. By providing detailed information across different environments, Loggly enables efficient issue tracking and resolution. It also aids in meeting auditing requirements by logging network activity and providing proof of network monitoring. Furthermore, Loggly is widely used to troubleshoot systems, gain insights into performance and health, and visualize trends through its dashboard and alarm capabilities. Whether it's monitoring web traffic, capturing logs to identify security threats on internal and external websites, or monitoring integrations between websites and APIs, Loggly proves to be an essential tool in enhancing monitoring capabilities. Its ability to capture the behavior of software applications during development allows for easier investigation and setting up alerts to prevent service disruptions. Loggly is considered a modern platform for log-file analysis due to its compatibility with Linux systems, plaintext config files, utilization of web standards, and open-source friendly nature. Overall, Loggly plays a crucial role in troubleshooting server and application issues by providing effective solutions for resolving problems.

Intuitive and Easy to Use Interface: Users consistently praise Loggly's intuitive and easy-to-use interface, stating that it simplifies tasks and makes them easier to perform. The user-friendly design allows for quick navigation and access to log data, enhancing overall usability.

Highly Effective Alerting System: Many users appreciate the flexibility and effectiveness of Loggly's alerting system, finding it easy to set up alerts for specific events. Notifications can be received through email or Slack, ensuring that users stay informed about critical issues in their applications.

Comprehensive Integration Options: Reviewers value the extensive integration options provided by Loggly, which support a wide range of log sources and platforms. This feature enables users to consolidate logs from different sources into a centralized location for monitoring and analyzing data effectively.

Confusing User Interface: Many users have expressed frustration with Loggly's user interface, stating that it is confusing and difficult to navigate. They find it challenging to perform tasks effectively due to this issue, which negatively impacts their overall experience with the platform.

Cumbersome Query Language: Some users have found Loggly's query language to be cumbersome and unintuitive. They believe that using the query language adds unnecessary complexity to their log analysis process, making it more time-consuming and challenging to extract meaningful insights from their logs.

Difficulty in Sending Logs: Several users have encountered difficulties when trying to send logs to Loggly, particularly depending on the source system they are using and the level of control they have over it. This has caused inconvenience for these users as they face challenges in seamlessly integrating their logs into Loggly for effective analysis and monitoring.

Users commonly recommend considering alternatives and exploring other options in addition to Loggly. They suggest looking into different logging and monitoring solutions before making a decision.

Another common recommendation is to ensure the correct data is inputted and to tweak the data sending process if necessary. Users advise being careful with the data that is being sent to Loggly and making any necessary adjustments to improve the accuracy of the logs.

Integrations and tools are also mentioned as important factors to consider. Users suggest looking into the available integrations and using tools to build the desired structure for log management and analysis.

It is worth noting that some users recommend spending time reducing log noise and standardizing the log entry process. They emphasize the importance of streamlining the logs to avoid unnecessary clutter and confusion.

Additionally, users suggest using Fluentd as an adapter to ensure Loggly receives all the necessary information. They find it helpful for ensuring smooth communication between systems.

Having someone knowledgeable who can provide training on Loggly is also recommended by users. They believe that having assistance from an expert can greatly enhance the user experience.

Organizing requests and their results is another recommendation made by users. They find Loggly useful in this regard, as it helps them keep track of their requests and easily access the corresponding results.

While many users find Loggly to be a good initial solution, some mention that costs can increase as usage grows. It is advised to keep this in mind when considering long-term usage of the platform.

Overall, users describe Loggly as an excellent solution for debug log management and analysis. They appreciate its functionality, especially with the addition of the live-tail client. Some users compare Loggly to LogEntries and note that they find Loggly to have better polish.

Attribute Ratings

Reviews

(1-25 of 36)
Companies can't remove reviews or game the system. Here's why
December 27, 2022

Solid and cost effective

Score 10 out of 10
Vetted Review
Verified User
Incentivized
SolarWinds Loggly is our standard logging solution for our entire cloud platform. If it is logged, it goes to SolarWinds Loggly.
  • Reliablity
  • Performance
  • Ease of use
  • Web search interface seems to periodically lose my saved tabs.
If you're not using a cloud logging platform of some type then stop what you are doing and switch immediately. As to choosing which cloud logging platform to use, I think that depends on your particular needs and which existing PAAS service provider(s) you already have. For our needs, SolarWinds Loggly is the best fit.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
At my organization we use SolarWinds Loggly to capture web traffic for roughly 60 internal and external websites. We do this through one simple SolarWinds Loggly integration on our load balancer and reverse proxy, NGINX. The traffic that SolarWinds Loggly captures, gives us insight into traffic patterns on our sites. It also gives us the ability to quickly identify security and peformance threats such as DDOS and Brute-force attacks.
  • Not surprisingly, SolarWinds Loggly does a great job of capturing logs.
  • SolarWinds Loggly has really good reporting and data filtering built into the system.
  • SolarWinds Loggly has alerting built into the platform that allows you to create custom notifications. The notifications allow you to proactively see an issue before it affects the end users.
  • SolarWinds Loggly has prebuilt plugins for some of the most common data sources. We've only needed the NGINX integration and it was really easy to setup and configure.
  • SolarWinds Loggly's customer service has always been responsive and easy to work with.
  • It would be great if you could setup SolarWinds Loggly to send a daily summary to your inbox so you can see yesterday's logs without having ot log into SolarWinds Loggly.
  • It would be nice to have the ability to share a report with a colleague or outside vendor via email.
SolarWinds Loggly is great for capturing and organizing logs from 3rd party sources such as NGINX. Without SolarWinds Loggly it's really difficult to manage the logs overtime, find traffic patterns, and identify issues before they become a problem. Anyone who is routinely searching through massive log files could quickly benefit from the SolarWinds Loggly and it's capabilities.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We have a lot of integrations between different websites and API's that run in the background. This is sometimes hard to monitor. We use SolarWinds Loggly to keep progress and error logs, fetch statistics on the amount of errors, and get notifications when errors occur. This improved our ability to monitor these integrations immensely.
  • Keeping logs from different integrations in 1 place
  • Being able to filter to find the relevant logs
  • Sending notifications when some logs occur
  • More options when setting up alerts would be welcome
  • Being able to update an alert query once it is created
  • When selecting 'view before and after events', keep the same search parameters (tags, for example)
SolarWinds Loggly is well suited for keeping track of your code to find the source of an error. If you structure your logs well, you can filter out all unnecessary logs and only keep the ones you need, so you can find the problem more quickly. It is less suited for detailed alert logic.
Score 9 out of 10
Vetted Review
Verified User
We use Loggly as a syslog digest. Normally it is an after-the-fact tool for outages and anomalies. Syslog is an invaluable tool when troubleshooting outages and errors. As we experience outages we go back and sift through Loggly to see what the messages looked like at the event time and create alerts based on them to catch the problems in advance the next time. As a secondary method of catching issues before they become problems, we monitor the gross volume of messages daily. When they spike on a given day we know that something is up and go and find the offending source. Many times we catch the problem before it causes a customer impact event.
  • syslog digest
  • alerts based on syslog contents
  • sanity check on number of daily log events
  • post mortem on outages
  • the interface could be more intuitive
  • repetitive syslog dialog could either be highlighted or ignored by user choice
  • when a source spikes it's name could be included in the volume alert email
Loggly is a great resource initially to post-mortem your errors and outages. After identifying the respective log events it can help you set alerts to keep you ahead of the game next time. When a box experiences a hard failure it can take days to recover the local syslog for troubleshooting but Loggly already has the messages. It greatly reduces time and even increases security since my team only needs Loggly access and not CLI-level authentication on all my servers. Overall, Loggly saves time, increases security, alerts me before my customers see the issues, and always provides the forensics needed to identify the root cause of an outage.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Our use of Loggly is mostly limited to storing debug/info/error logs from our software in a format that is both easily searchable and secure.
  • We love that we get 1gb of log storage per day (a limit we'll probably never even come close to touching)
  • We are able to send alerts based on thresholds that we set.
  • The Search feature is very powerful and it allows you to save searches.
  • The UI is a bit outdated.
  • Longer log storage would be great.
Great for getting logs off of your servers and in the cloud.
Score 4 out of 10
Vetted Review
Verified User
Incentivized
We needed a well rounded platform to aggregate system logs from all cloud platforms. Loggly provided this and made it easier to quickly troubleshoot issues in the virtual environment and give us a dashboard to view them. Triage of alerts is made easier using the event timeline feature of Loggly and helps to bring down our repair time.
  • Customizable Dashboards
  • Azure integration
  • Webhook integration
  • Cost
  • Speed of support
  • Better searching
  • Better user management
Loggly was not the best solution overall for us to use. It is more for heavily invested Azure and AWS companies. We had one Azure client but they have since moved to on-prem as the costs were to high. With everyone else on prem, it has not been worth it for us to continue to use Loggly. We used other solutions and will continue to that better meet our needs.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Loggly is currently being used in one of our systems for troubleshooting server and application issues and to making sure our transactions correlate. Currently, it is only in one of our systems but it will definitely expand to our other systems due to the powerful troubleshooting and very fast searching capability of Loggly.
  • Very fast searching capabilities.
  • Easily handles huge volumes of logs.
  • Searches are not always very intuitive.
  • User management is not the best.
Loggly is an easy-to-set-up log management tool and very well suited for those times where you need to aggregate logs from various sources and systems into a central location where they can be centrally searched, monitored, analyzed, and/or filtered to help maintain uptime on various systems. Loggly would not be as appropriate for companies that produce embedded systems.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We have several apps running on AWS EKS (Kubernetes on AWS), and we've used Loggly as a central repository of the logs for PHP-based apps with different frameworks, and also for the server running these apps. At the time of implementation, AWS didn't have a good central logs tool with reports, aggregate, and analysis from different sources taking into account that this application runs in autoscaling and highly available containers that are being constantly replaced.
  • Multiple sources for the logs, the amount of log sources available in Loggly is amazing! You can log from almost everything you can have running out there.
  • The charts and dashboards, it's really easy to find and see the information you need to find problems you might be having without noticing.
  • Centralization and aggregation, having multiple auto-scalable microservices running Loggly makes it really easy to centralize and aggregate all the data coming from these microservices.
  • The volume pricing scheme is tricky, as usually, you don't need more features but just more volume. I think a big improvement would some per/GB/MB pricing scheme if the volume is so important and not the 200MB, 1GB, and 100GB per day jumps that forces you to be controlling how much you log because, usually in the case of an incident, you can have more than 1GB per day but then on a normal day volume can fall below 200MB.
I think Loggly is a really strong solution when you have a lot of different sources of information (applications, services, cloud infrastructures) that you need to centralize to correlate in case of incidents, audits, or application improvement.
December 15, 2020

Loggly rocks

Score 8 out of 10
Vetted Review
Verified User
Incentivized
Loggly is a neat a straight forward product. We use to centralize most of our application and security logs, including WAF data which we then transform into nice dashboards for quick overviews
  • Ingestion
  • Dashboards
  • Alerts
  • User management
  • SSO
Setup is quick and easy, and Loggly documentation already provides the necessary steps for most systems.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use SolarWinds Loggly extensively in our cloud offerings, not across the whole organization. Using Loggly allows us to focus on real business needs, instead of development and management in-house log solution. Loggly helps a lot with troubleshooting searching, filtering, usage analysis, and graphical presentation of logs. The best feature is easy narrowing down of results by log message parameters.
  • Intuitive step-by-step filtering by message attributes.
  • Collapsing/extending log event data.
  • Flexible log list presentation with selection of attributes to present.
  • Graphical presentation of log events.
  • Ability to filter out specific type of messages from the list to focus on important ones. Filter by example.
  • Ability to send separate streams with cheaper cost and deeper storage, slower access times on demand only in specific cases.
Works well, helps to focus on real business.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Loggly is being used by all of our applications across the company by our engineering staff. Loggly helps our engineers accurately filter and sort logs to help debugging test and production code. To help our engineers with debugging their code our Loggly system is setup to work with SolarWinds AppOptics to pin-point errors when they occur.
  • Easily takes sys-log connections from an app's standard output.
  • Easy to navigate the user interface.
  • Begins ingesting logs as soon as the connection to an app is made.
  • Having to add users to Loggly after having created them in AppOptics could be improved.
  • When search parameters are too specific Loggly often has a hard time filtering for what I'm looking for.
  • While it's easy to navigate, the UI isn't very pretty.
SolarWinds Loggly is well suited for an business that needs a logging system that integrates with an APM system. SolarWinds has made a great effort to tie their systems together to help companies maintain uptime across their systems. Loggly would be less appropriate for companies that manufacture embedded systems for example.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
As we provide a PaaS to both internal employees and our partners, SolarWinds Loggly is essential to monitoring and diagnosing our cloud-based infrastructure. It's been essential for both our development team and our IT group to monitor usage and performance while also identifying and resolving any issues that come up.
  • Fast setup and deployment.
  • Very customizable.
  • Searching and sorting relevant data is intuitive.
  • It's not free.
  • Won't run stand-alone on-premises.
  • Doesn't look as slick as some other alternatives.
Loggly is primarily useful for combining logs into one centralized location. The insights that the dashboards provide also allow us to identify bottlenecks between microservices. We've had multiple instances where the ability to filter logs by keywords and seeing multiple servers' logs at the same time helped identify problems immediately. This has saved us days of troubleshooting.
October 02, 2020

Fire and forget logs

Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Loggly as an aggregation point to stream logs from network access switches and core routers. There can be quite a lot of data and existing solutions relied on older database technologies which broke down after a time and we'd have to manually intervene to truncate tables, etc. Loggly manages the entire process for us and just works.
  • Keeps working!
  • Fast searches.
  • Easy to configure searches - you don't have to be an expert in RegExp...
  • Not all searches are intuitive.
  • We have to use a log aggregating device to ship our logs to Loggly as our network devices can not connect on an encrypted protocol. I would prefer if we could use some sort of VPN-based connector to ship logs securely.
  • Sometimes when drilled down, it can be difficult to fully reset a search term to back all the way out of a drill down.
It is well suited to very large volumes of logs where the immediate past is the area of interest, e.g. in situations where the issues are in the recent past. Loggly makes it very easy to search for particular terms of interest, within a specific time frame across the entire estate of devices or, indeed, within a subset, or on a specific device of interest. There does seem to be a short delay in the logs though, even with the "live tail" feature, Loggly might be less suited to "emerging" situations where the issues are occurring in real time.
Simon Clarke | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We previously had a very disjointed way of gathering, searching and responding to issues that where logged from our systems and apps, implementing Loggly across the whole of our server estate has enabled us to track down issues quickly, allowing them to be dealt with efficiently and with minimal issues to the company.
We are able to log different areas of the business, grouping systems and apps. this allows our searching and history tracing for logs to be much more effective.
  • The collection tools for Loggly are very strong and the setup for those tools is incredibly easy.
  • Support are fairly quick to respond and super helpful.
  • Capturing and interrogating logs is easy across many deployments, platforms and devices.
  • Sometimes queries don't work as you think they should.
  • Getting data arranged so that everything comes to play is fiddly.
  • Daily data limits can be a pain if you have a spike in logging.
Loggly was brought in when we where trying to trace issues down on our domain, by having it implemented across our Domain Controllers, we were able to find and resolve our known issues very quickly.
The querying system could do with a better FAQ or guidance as when trying to run a structured query, sometimes no data is found even though you can definitely see that data by manual search.
Score 6 out of 10
Vetted Review
Verified User
Incentivized
Loggly allows us to collect the logs from our various services in our solution and see them in one place.
  • Loggly is easy to integration. If you can make JSON from your logs you can use it. Adding it to a Python stack was trivial. Standard python logging, Loggly backend.
  • Easy user management to allow people see view the logs.
  • Documented API to retrieve and query the logs.
  • The search interface. It remembers the last time window you chose. So you constantly are looking at the wrong logs.
  • Everything is chunked on words. So searching for say an email address does not consistently work be it breaks someone@somewhere.com into someone, somewhere, com.
  • filtering in the results is quite limited. Copy and paste is often broken by how the results are displayed.
  • Finding the link to share a particular log is a process of frustration of finding just the right place to click to make the buttons appear.
Having all of the data in great. Not being able to find it is not so great. The promise of charting is alluring but it is hard to create charts that show what I am interested in seeing. I currently sift through the site but also do a fair amount using the API instead.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use SolarWinds Loggly to monitor one specific server. Our clients need us to deliver reliably and thorough monitoring is essential for reliability. Monitoring the log files of the server helps us to detect issues before they affect the system.
We monitor operating system, web server and application logs. This allows us to detect load peaks, issues in the application, attempted attacks or any other anomalies early.
  • A key feature for me is drilling down logs, finding what I am looking for quickly.
  • Creating graphs and dashboards for important information at a glance.
  • Setting alarms in case something unexpected happens.
  • Adding log sources is easy.
  • Users that want to use Loggly to its full power need to invest some time.
  • It's not very cheap.
  • I struggled adding logs with dynamic names.
I think that Loggly is suitable for all projects where constant and reliable log monitoring is needed and where the price matches the project's capacity. The price might be a show stopper for smaller companies or projects.
Loggly is also very good to monitor logs from many servers at once, a feature that I don't use but would recommend doing if applicable.
Score 4 out of 10
Vetted Review
Verified User
Incentivized
Loggly was used by a particular department/product line. It was used only at the free tier and by a team with minimal operations experience. The setup and configuration were very simple and straight-forward. It enabled centralized log management for a team that otherwise wouldn't have had this in place. Ease of use and free tier were the primary factors in the decision to use this service.
  • Ease of setup
  • Intuitive UX
  • Response times are fast
  • The system seemed to lack the power (AI anomaly detection) of other offerings, but we were only on the free tier.
  • No advanced features were evaluated.
For a small team looking to get up and running quickly, it's perfect. For more advanced teams with dedicated staff, I'd probably not recommend this solution and stick with the heavy hitters in this vertical.
September 29, 2020

Loggly is good

Score 9 out of 10
Vetted Review
Verified User
Incentivized
We are a small startup that makes training and marketing software. Our platform is our entire business, and we use Loggly for a few things:

* Aggregating all of our logs.
* Deriving metrics from our logs.
* Sending alerts to our team when those metrics change in some way that matters to us.
  • Putting our logs in one place and making them searchable. We use AWS, and CloudWatch has always been a little frustrating in this regard (though it has gotten better recently).
  • Deriving metrics from our logs. I think log-based metrics is such a good idea because your logs are the ultimate source for truth in regards to what the hell is going on inside your app. I have really loved the simplicity with which I can just count certain statements and call that a metric because just through the normal course of development certain log statements just naturally become a straightforward recording of an event having occurred.
  • Alerts. I actually have a few complaints about email alerts, but just the way I was able to set them up so easily has been huge. Since we started using Loggly, there have been at least 3 bugs that Loggly exposed that were frankly very bad. And withoutt Loggly or without a user reporting them, we would have never known they were happening! This is stuff I tried to set up in CloudWatch in various ways, but because of my own ignorance or perhaps the complexity/limitations of CloudWatch (or the complexity of my stack?), I wasn't getting the information that I needed until I was able to just tell Loggly to send me an email whenever the word "error" showed up.
  • I would love the ability to able to suppress a particular "event" instead of an entire alert. For example, sometimes an error is caught and handled but the word "error" is still printed to the logs. It would be nice if I could mark an event as "handled" without suppressing the entire alert for n minutes- if I do that then I would miss a real error that happened in that window. Also if I have my alerts set to run every minute checking the last five minutes, I will get 5 emails. It would be nice if there was some de-duplication. I have actually considered setting up webhooks into some API of my own instead of just emails to do this.
  • I find the query language to be a little cumbersome. I suspect this is something you guys inherited from whatever index you use, but things like the __exists__ flag are strange. If I just type something into the field I am often surprised that I have to put quotation marks in (instead of it just searching for the term I supplied without any advanced features).
  • Derived fields sometimes frustrate me, especially when I am using regex. I will sometimes create regexes that work in a test bed but do not work in Loggly. It is frustrating that I always have to match the beginning and the end of the string.
  • The dashboards can be frustrating, especially when I am just trying to put a single number metric in a chart. I should be able to create a chart with multiple metrics: multiple charts with a single metric in each takes up a ton of space and limits the usability of the dashboard
I think even for a small organization, and perhaps more so for a small organization, Loggly would be super valuable. There have been several issues that we simply wouldn't know about without Loggly. I lose sleep over that. Our stack isn't *super* complicated, but like (I suspect) many, even a relatively uncomplicated stack can generate a ton of logs from disparate sources. For example, I often use lambdas for "glue code" and without a centralized Loggly tool tracking what is going on in some of these flows was very difficult. The alarms are great. Some of my complaints in the last screen are the only thing preventing me from giving it a perfect 10.
Score 6 out of 10
Vetted Review
Verified User
Incentivized
Loggly is one of the ways that allow us to possibly capture the behavior of our software applications both during development and when they are running live. Our Development Teams can add logging to their code and they and site reliability engineers can investigate when the information is logged. Incident management has set up some alerts against particular messages to possibly warn before potential service disruptions occur.
  • It can log whatever a developer decides to add information about.
  • Zooming in on a particular time frame is helpful.
  • The ability to tag/label events.
  • Once the logging limit is exceeded, there are no logs period. Unexpectedly noisy logs often correlate with services misbehaving and potentially leading to disruption. An outage is an awful time to lose visibility into the entire system of apps. Some ways to bridge this gap would be appreciated.
  • Filtering by tags is not intuitive in the web interface. You may believe that you are performing the same search and filter as last time since the tags entered are the same, however, this is often not the case. The reliable way to know that you have the same filter is to bookmark the URL. This lack of ease in usability results in devs using Loggly less than they could and implementing logs less effectively during development time (since they don't consider themselves likely to view them anyway).
  • Would like to see a way to onboard our less experienced devs to using Loggly effectively.
This is a good choice if you have developers that understand using logging levels appropriately (i.e. not simply blasting every possible piece of information to logs, knowing to use debug and info levels). If you have people who know how to set up alerts based on logs, you can find it very useful also. However, if you are missing a critical mass of this experience and skill level at your organization, you'll find your logs are very noisy and hard to search through for what you want, subsequently degrading devs' enthusiasm for learning and using them. Furthermore, you may often hit your logging limit and lose logs during critical times. Use this solution if you're confident your technical folks are up to speed on effective logging practices.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use Loggly to satisfy a compliance requirement for centralized logging. Loggly is used on every PC across the whole organization to aggregate logs for auditing, analytic, and alert purposes. We also push logs from firewalls, switches, and wireless access points for network log visibility. Loggly helps identify patterns and anomalies that may otherwise be undetected.
  • Creating alerts for specific events is very easy.
  • Data visualizations are easy to configure; some are baked in.
  • The price of Loggly is well below all other cloud logging tools I reviewed.
  • Extra pre-baked dashboards would be useful.
  • Searching for multiple conditions sometimes fails even when each of the fields can be found individually within a log message.
  • Documentation to configure S3 archives needs to be updated to reflect the current Loggly GUI options.
Loggly is best suited for large organizations where laptops are frequently taken into the field where users may neglect to connect to a VPN back to a facility with onsite centralized logging. The price also makes Loggly attractive as the features match other higher priced solutions. Loggly is very easy to configure, deploy, and tweak when compared to other major hitters like Graylog.
September 10, 2020

Great tool, love it!

Tomer Sofer | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We are using Loggly to troubleshoot our systems and getting better understanding about our overall performance and health. This tool helps us visualize simply trends by using its dashboard, tracks occurrences and even as monitoring tool by leveraging its alarms capabilities. As of today Loggly is being used in many LivePerson business units however some are using different tools like Kibana for example.
  • Simple search.
  • Great visualization.
  • Easy to use.
  • Very practical.
  • Maybe examples of advanced filtering.
Every respectable software company would log its application for tracking and monitoring. In many cases, developers tend to log too many things and eventually it's becoming a mess to understand what is going on. Loggly is helping you to find what you need easily inside all of this pile of information and that's not trivial.
I can think only about the benefits at this point:
1. Investigate production issues.
2. Visualize trend.
3. Count occurrence.
4. Exporting data.
Tyler Carter | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
SolarWinds Loggly is used by the IT department. The chief focus is logging application errors and warnings to be able to detect problems with our system, as well as understand informational messages surrounding those warnings and errors.
  • Detecting logs messages for alerts
  • Log drill-downs through attributes
  • Bringing various sources together
  • Charts/metrics
  • Understanding and adapting to specific formats
  • Docker system ingesting
Logging application output for several applications or across different systems is done well with SolarWinds Loggly. Single applications are overkill. Charts and metrics are not its strong suit, but instead, the primary strength seems to be identifying individual log messages instead of tracing. Good at alerting for particular problems.
Score 5 out of 10
Vetted Review
Verified User
Incentivized
My company was looking for a centralized logging platform so we tested with Loggly. It was being used by our IT team to monitor network devices as well as security and by our developers to monitor certain Windows event logs, as well as database logs.
  • Centralized logging: having logging for multiples sites (networks) all under one roof was really nice.
  • Customer support: the customer support was outstanding when we had issues with our deployment of our first nxlog configuration.
  • Ease of use: though there is a small learning curve, once conquered, Loggly becomes a very handy tool when needing to pull up past events or logs.
  • nxlog: having to use another piece of software is a bummer
  • nxlog configuration: the learning curve for nxlog is monumental and not very intuitive
  • 1:1 Alerting: Loggly does not support this which is ultimately why my company is looking elsewhere. The alerting does not mesh well those who want login and logout alerts in real-time
I feel Loggly is designed more for the developer's side of things. Loggly was clunky to implement for network device monitoring and didn't meet our needs when it came to security alerts. Though checking for Windows event logs or any sort of process logs it is a breeze, it did not check all the boxes it needed to for us to implement.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
SolarWinds Loggly is used by our IT Operations as well as the Engineering department. We use it to troubleshoot and monitor our application. It's used to notify the proper people for certain errors and issues.
  • Makes viewing logs more readable.
  • Allows us to pull logs from different sources.
  • Search is good, when you know how to use it.
  • Support is not the best, it's only email and they won't get on a remote session with you.
  • Bit of a learning curve to get started.
  • Had issues with getting CloudWatch logs, had to escalate to a higher support rep.
SolarWinds Loggly is well suited for monitoring application and service logs. Great to track down errors so long as your app exposes them! It does a great job as long as you have the log sources piped through properly. Where it's less appropriate is probably for Windows Security Events, that would be more for a SIEM.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We used it to aggregate logs from all our servers, mostly for DevOps and debugging purposes. I didn't do the initial setup so I don't know how much effort it takes. But it sure is easy to maintain.
  • Quick customer supports. I found an issue and the customer service provided some workarounds before the final fix.
  • Easy HTTP integration. I integrated into my own Lambda function so I can process logs with my own logic.
  • Speedy (majority of the time).
  • Clean UI.
  • Cooler Charts/Dashboard.
  • More intelligent input prompts.
It's an easy-to-set-up log management tool. Big enterprise might want to set up their own ELK stack because one stack, but for smaller companies, the opportunity cost is much lower to manage logs with commercial solutions like Loggly or its alternatives such as Splunk.

When I was in my previous company there were teams taking care of the ElasticSearch and Logstash so I only needed to use Kibana. In my current startup, I feel it's easier to use Loggly.
Return to navigation